2014-12-15 - 16150.200 -Spec - Negative Quantities in Contract Cube #SalesDistribution
SPECIFICATIONS
16150.200 - Negative Quantities in Contract Cube
Purpose
The contract infocube ZSD_CONTR has negative quantities due to errors in the routine logic in BW.
Admin Info
Purpose
|
Negative Quantities in Contract Cube.
|
Requested By
|
Mark Harris
|
Spec Created By
|
Naveen G
|
Spec Created Date
|
12/12/2014
|
Spec QA by
|
Uday Kumar P
|
Objects
|
ZSD_CONTR
|
Document Status
|
Complete
|
Estimates
SNo
|
Activity
|
Estimation in Hours
|
1
|
Research
|
10
|
2
|
Documentation
|
10
|
3
|
Development/Config
|
10
|
4
|
Unit test in DEV
|
30
|
5
|
Unit test in QUA
|
12
|
6
|
Transports
|
08
|
|
TOTAL
|
80
|
References
Prior Tickets
16150.100
Documents
None
Spec Changes
SNo
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
01
|
If Order, Material & Grid Value have 2 dates then which date copied to Call Offs.
|
Greg Jackson
|
12-18-2014
|
Implemented in Same Release Note.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
Email from Greg on 12/03/2014:
I had sent you an email this morning about negative quantities, but this email and the first one from this morning are two different issues I believe. This issue is negative quantities in the Contract cube [ZSD_CONTR]. The quantities here are positive in the ZAFSDDS1 DSO and then through the transformation get turned into negatives. You can use sales doc 2138458 as an example, but the issue is with quite a few Japan orders.
In Scope:
Open Contract orders along with their valid Call Offs.
Out of Scope:
Sales Orders that are not under contracts.
Solution Summary
The logic for copying the Contract AFS Desired
Delivery Date, Schedule line delivery date and AFS Order Cancellation date to its calloff's is based on Sales Document, Item & Schedule line. If this logic fails due to mismatch then AFS Desired
Delivery Date, Schedule line delivery date and AFS Order Cancellation date are populated with blank dates for a call off resulting in negative quantities in the contract cube. Due to the current logic the contract reference Quantities don't match in some case with the ECC results.
1. Need to change the logic in the start routine of Contract cube based on Sales Order, Item, Schedule line, Material & Grid value. if the above logic fails then check based on Sales Order, Item, Material & Grid value & if the above logic also fails check based on Sales Order,Material & Grid value to copy the Contract AFS Desired
Delivery Date, Schedule line delivery date and AFS Order Cancellation date to its Call off. If the above logic fails, need to delete the record from the source package considering it as invalid.
2. Need to apply the same logic in the corresponding regional infoubes for the contract source.
3. Need to test the new logic in all the possible test scenarios specified by SD Team & NEC as specified below.
4. Need to check the infocube results and reconcile them with ECC.
5. Need to collect new logic and related objects into the transport request.
Test Plan
Please find the attached spreadsheet for the list of test cases in NECNED300 specified by SD Team:
Contract Test Scenarios - NECNED300.xls
Please find the attached spreadsheet for the list of test cases in NECNEQ100 specified by SD Team:
Contract Test Scenarios - NECNEQ100.xlsx
SNo
|
Test Scenario
|
Expected Results
|
1
|
Check if the previous logic is removed from the start routine.
|
Previous logic need to be removed from the start routine.
|
2
|
Check if the new logic is replaced in all the necessary dataflows.
|
New Logic has to be replaced in all the necessary dataflows
|
3
|
Check if all the objects are collected into the transport request.
|
All the objects should be collected into the transport request.
|
Solution Details
1. Need to change the logic in the start routine of Contract cube(ZSD_CONTR) based on Sales Order(0DOC_NUMBER), Material(0MATERIAL) & Grid value(0AF_GRDVAL) to copy the contract AFS Desired
Delivery Date(0AF_RQDATE),
Schedule line delivery date(0REQ_DATE) and
AFS Order Cancellation date (0AF_CADATE)
to its Call off. If the above logic fails, need to delete the record from the source package considering it as invalid.
2. Need to apply the same logic in the corresponding regional infocubes(Z_CNTR03, Z_CNTR04 and Z_CNTR05) of the contract source.
3. Need to test the new logic in all the possible test scenarios specified by SD Team & NEC.
4. Need to check the infocube results and reconcile them with ECC.
5. Need to collect new logic and related objects into the transport request.
Issues
None